Characteristics of a Class and a Use case | Service Principles and/or Definitions | Mapped service characteristic to Service Definitions and/or Principles |
Each class represents a tangible or real-word things, roles, events, interactions. They accordingly describe a set of objects with an equivalent role or roles in a system | Entity Service definition | The functional boundary of service is based upon one or more business entities. |
Each group of classes are dependent on each other where they are immediately related through association or generalization relationships. However, each identified group have relatively lower dependency on other groups where relations between them don’t exceed read relationship. | Principle of Loose Coupling | Each service has low dependability on other serice. |
Each class defines an abstract description of a group of concepts that encapsulates functionalities and behaviours | Principle of Abstracting Underlying Logic | Each service acts as black box, where they abstract the underlying functionalities that are considered service capabilities. |
Classes are concerned with one or more related entities, allowing classes to be reused, through the object orientation cocncepts such as inheritance and polymorphism | Principle of Reusability/ Principle of Composability | Identified services are highly reusable and are composable. The granularity level is not too coarse-grained nor too fine-grained. |
Classes are related through association, generalization and composition relations (i.e. relations between class are not conversational). | Principle of Statelessness | Services minimize the amount of state information they manage. |